Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551cd6ef47e1b58e4f352e7c6625c910de5b9777312d60cb06269890631f7c10

Tx prefix hash: 794d4f6d3a315aa4832f6d36dcddda7cbecb3a771c05d2e2b55cf67f97e24615
Tx public key: fbb7fd8a218e64ac3447d3089504c13e6514a9d57482fb3531b75dc19d4a46dd
Timestamp: 1696665853 Timestamp [UCT]: 2023-10-07 08:04:13 Age [y:d:h:m:s]: 01:192:21:59:40
Block: 864301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398932 RingCT/type: yes/0
Extra: 01fbb7fd8a218e64ac3447d3089504c13e6514a9d57482fb3531b75dc19d4a46dd02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.839869934000 dcy

stealth address amount amount idx
00: 709e1e3dbfdc46a6d02bffa9568ba0f028d9d2f883624244cf791fa657947570 0.839869934000 1318813 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": 864311, "vin": [ { "gen": { "height": 864301 } } ], "vout": [ { "amount": 839869934, "target": { "key": "709e1e3dbfdc46a6d02bffa9568ba0f028d9d2f883624244cf791fa657947570" } } ], "extra": [ 1, 251, 183, 253, 138, 33, 142, 100, 172, 52, 71, 211, 8, 149, 4, 193, 62, 101, 20, 169, 213, 116, 130, 251, 53, 49, 183, 93, 193, 157, 74, 70, 221, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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