Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e374f09a1fb1b231de2ee7582062066854c5eb631960ce8891f498f8056b4b

Tx prefix hash: ef14ae3f530a5568a0158039cf049a2a94fe46f2b9e12cebf7c5eff65587541c
Tx public key: 4a8f65c89e97d9bc1c3feba28c648a6f74e254c997410fd176aef56563aec4d2
Timestamp: 1732446066 Timestamp [UCT]: 2024-11-24 11:01:06 Age [y:d:h:m:s]: 00:133:17:26:31
Block: 1160640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95379 RingCT/type: yes/0
Extra: 014a8f65c89e97d9bc1c3feba28c648a6f74e254c997410fd176aef56563aec4d20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2863fe66db617ea9e86efa1818f604073bd8bf71066f300af0e7d88e25696f29 0.600000000000 1646287 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": 1160650, "vin": [ { "gen": { "height": 1160640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2863fe66db617ea9e86efa1818f604073bd8bf71066f300af0e7d88e25696f29" } } ], "extra": [ 1, 74, 143, 101, 200, 158, 151, 217, 188, 28, 63, 235, 162, 140, 100, 138, 111, 116, 226, 84, 201, 151, 65, 15, 209, 118, 174, 245, 101, 99, 174, 196, 210, 2, 17, 0, 0, 0, 3, 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