Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7be43c98ed79095ad8ff2f1abae5c2a4d5fc4a7ee4ff1b479636a1aaa710b4f

Tx prefix hash: 57628e31fc15f9883738d60db169677f275f32f548cd93cc6947ce1bde286b47
Tx public key: 609da6f843940f115b898b3d036f9c5849cad3afe89a35cb1fbd72b8a2c955c0
Timestamp: 1736322415 Timestamp [UCT]: 2025-01-08 07:46:55 Age [y:d:h:m:s]: 00:348:06:06:06
Block: 1192739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246452 RingCT/type: yes/0
Extra: 01609da6f843940f115b898b3d036f9c5849cad3afe89a35cb1fbd72b8a2c955c002110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81b578c7c0d9c1d97103497ed39980aef66ede4e29ac515924e5702cf058eae0 0.600000000000 1679294 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": 1192749, "vin": [ { "gen": { "height": 1192739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81b578c7c0d9c1d97103497ed39980aef66ede4e29ac515924e5702cf058eae0" } } ], "extra": [ 1, 96, 157, 166, 248, 67, 148, 15, 17, 91, 137, 139, 61, 3, 111, 156, 88, 73, 202, 211, 175, 232, 154, 53, 203, 31, 189, 114, 184, 162, 201, 85, 192, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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