Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73565ff81110c2db2d076640e259e3f985e3004de6de6ea321025a096870692d

Tx prefix hash: 688018871efc2daf78ca9a1f0fb2dab948c4af18d705829214f0dcd3925314b6
Tx public key: d8c9ccd8d0775f72319d1a84c2c05835c4c67404b2f62dfcfe1aba554e21974c
Timestamp: 1738926686 Timestamp [UCT]: 2025-02-07 11:11:26 Age [y:d:h:m:s]: 00:285:20:50:03
Block: 1214042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202065 RingCT/type: yes/0
Extra: 01d8c9ccd8d0775f72319d1a84c2c05835c4c67404b2f62dfcfe1aba554e21974c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566d5039687bc737dffb51d45eeb4f09c81823e8ec4e7de6b7c3458486095fad 0.600000000000 1700827 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": 1214052, "vin": [ { "gen": { "height": 1214042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566d5039687bc737dffb51d45eeb4f09c81823e8ec4e7de6b7c3458486095fad" } } ], "extra": [ 1, 216, 201, 204, 216, 208, 119, 95, 114, 49, 157, 26, 132, 194, 192, 88, 53, 196, 198, 116, 4, 178, 246, 45, 252, 254, 26, 186, 85, 78, 33, 151, 76, 2, 17, 0, 0, 0, 3, 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