Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ee55847214c3ca3dc52cabc68a0446f4b6e1874bdc5b7323435a9c896103c1d7

Tx prefix hash: f60f8f9c2a18df6ee24c747095667f65216c60017e26e7e6e3772bff3e0f349d
Tx public key: 0079cc13262461031b8c9fc65f4054ff550df9efefa669e98306abd94a6a40ce
Timestamp: 1574105445 Timestamp [UCT]: 2019-11-18 19:30:45 Age [y:d:h:m:s]: 05:009:16:23:07
Block: 12097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1150002 RingCT/type: yes/0
Extra: 010079cc13262461031b8c9fc65f4054ff550df9efefa669e98306abd94a6a40ce02110000000166a80d00000000000000000000

1 output(s) for total of 559.652574208000 dcy

stealth address amount amount idx
00: 0b1e98bc7996fded1689c4e5a8df9c0a76c578a081cd109acdd4bbc28cf7614b 559.652574208000 13184 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 12107, "vin": [ { "gen": { "height": 12097 } } ], "vout": [ { "amount": 559652574208, "target": { "key": "0b1e98bc7996fded1689c4e5a8df9c0a76c578a081cd109acdd4bbc28cf7614b" } } ], "extra": [ 1, 0, 121, 204, 19, 38, 36, 97, 3, 27, 140, 159, 198, 95, 64, 84, 255, 85, 13, 249, 239, 239, 166, 105, 233, 131, 6, 171, 217, 74, 106, 64, 206, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8