Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623c6d68378dadf873545af5d363cc966469523b35e37f988c9193723babcb82

Tx prefix hash: d1ff54b8bea5deedb36252c9db7c3e0b12ab0b1a497c97938e43155e78714978
Tx public key: c479553e580234e98f9b1b8bc26dc19cf36932d9db6f76894b024f1152b9da3b
Timestamp: 1729298018 Timestamp [UCT]: 2024-10-19 00:33:38 Age [y:d:h:m:s]: 00:239:11:28:17
Block: 1134641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170874 RingCT/type: yes/0
Extra: 01c479553e580234e98f9b1b8bc26dc19cf36932d9db6f76894b024f1152b9da3b02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 052e2777093c9d8b1e34760514c21c4acb5eef8d799c0e2c455fddd7170f37d6 0.600000000000 1617966 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": 1134651, "vin": [ { "gen": { "height": 1134641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "052e2777093c9d8b1e34760514c21c4acb5eef8d799c0e2c455fddd7170f37d6" } } ], "extra": [ 1, 196, 121, 85, 62, 88, 2, 52, 233, 143, 155, 27, 139, 194, 109, 193, 156, 243, 105, 50, 217, 219, 111, 118, 137, 75, 2, 79, 17, 82, 185, 218, 59, 2, 17, 0, 0, 0, 10, 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