Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a1aa695aed388924a84ff71b5cc57228d9f56e191c4d35f894710be6fca527

Tx prefix hash: 455804203e229068e54b89fbbaaada3c2b56ed9ed55ad990242748b21b9656ca
Tx public key: b59f09ffdff9ea96b6d1d69f20070e2102b0a37929d27ff8767d7dd276c87a0b
Timestamp: 1735875156 Timestamp [UCT]: 2025-01-03 03:32:36 Age [y:d:h:m:s]: 00:090:21:28:16
Block: 1189035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64748 RingCT/type: yes/0
Extra: 01b59f09ffdff9ea96b6d1d69f20070e2102b0a37929d27ff8767d7dd276c87a0b021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a46c459b741b6237554b2a3c3d842aba71d52bcae844a57c90f7530334dcfa92 0.600000000000 1675540 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": 1189045, "vin": [ { "gen": { "height": 1189035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a46c459b741b6237554b2a3c3d842aba71d52bcae844a57c90f7530334dcfa92" } } ], "extra": [ 1, 181, 159, 9, 255, 223, 249, 234, 150, 182, 209, 214, 159, 32, 7, 14, 33, 2, 176, 163, 121, 41, 210, 127, 248, 118, 125, 125, 210, 118, 200, 122, 11, 2, 17, 0, 0, 0, 8, 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