Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f34fbad88e0c1871fb5a4e991a8d88d54402ede3566aeb69cbe68318df8e13

Tx prefix hash: cf86886565b66bc8414e3651bfb4b28515ddbc66929e26a1142e5e6375a62e4c
Tx public key: 73923be99576def1779a4084492d7aeee716e37e3ea7d9dae77d2dcb80b42649
Timestamp: 1740789238 Timestamp [UCT]: 2025-03-01 00:33:58 Age [y:d:h:m:s]: 00:265:23:48:02
Block: 1229439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187866 RingCT/type: yes/0
Extra: 0173923be99576def1779a4084492d7aeee716e37e3ea7d9dae77d2dcb80b42649021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a284e9c800a7d5af4dffa7778e126f49a43cf1994ccdcc98b0e98ad24a4d0451 0.600000000000 1716326 of 15

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": 1229449, "vin": [ { "gen": { "height": 1229439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a284e9c800a7d5af4dffa7778e126f49a43cf1994ccdcc98b0e98ad24a4d0451" } } ], "extra": [ 1, 115, 146, 59, 233, 149, 118, 222, 241, 119, 154, 64, 132, 73, 45, 122, 238, 231, 22, 227, 126, 62, 167, 217, 218, 231, 125, 45, 203, 128, 180, 38, 73, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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