Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c03598d367ab3919d8106d96935dcce29846caa705f8809bf9cf22ec0ac531

Tx prefix hash: 4e654f910e51b3a1839ad04f017e24fde9b9296c419d29e56b8669e6e6f3b6dd
Tx public key: ed5e0f12c5793371c25b9ddc6e4784f536b196ee6a2dbb475305cf8d77473e58
Timestamp: 1714051195 Timestamp [UCT]: 2024-04-25 13:19:55 Age [y:d:h:m:s]: 00:341:13:56:00
Block: 1008236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244170 RingCT/type: yes/0
Extra: 01ed5e0f12c5793371c25b9ddc6e4784f536b196ee6a2dbb475305cf8d77473e580211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d175d6d98e8ef89882813228efbfc80d97df48b2229fe3772bd71130f1bbb8 0.600000000000 1469704 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": 1008246, "vin": [ { "gen": { "height": 1008236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d175d6d98e8ef89882813228efbfc80d97df48b2229fe3772bd71130f1bbb8" } } ], "extra": [ 1, 237, 94, 15, 18, 197, 121, 51, 113, 194, 91, 157, 220, 110, 71, 132, 245, 54, 177, 150, 238, 106, 45, 187, 71, 83, 5, 207, 141, 119, 71, 62, 88, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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