Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488d189c65eb9e7dd0a7f6bb014a17c5678fdfc5cb3a77f2f894cf378471534d

Tx prefix hash: 463effadfa46b01c4760a5ffdf8ef17fab30934cf3179f246ac35132f1d8736d
Tx public key: 09b0fccfcab69e2d528889ee90520257927ff83e85eb726c478b61e4195c7fb0
Timestamp: 1737568232 Timestamp [UCT]: 2025-01-22 17:50:32 Age [y:d:h:m:s]: 00:145:22:23:13
Block: 1203014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104041 RingCT/type: yes/0
Extra: 0109b0fccfcab69e2d528889ee90520257927ff83e85eb726c478b61e4195c7fb0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca0679e5d05a39cb7f4e6a4ff9df66bd4025996190244ab0d7848a0d820db4b 0.600000000000 1689685 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": 1203024, "vin": [ { "gen": { "height": 1203014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca0679e5d05a39cb7f4e6a4ff9df66bd4025996190244ab0d7848a0d820db4b" } } ], "extra": [ 1, 9, 176, 252, 207, 202, 182, 158, 45, 82, 136, 137, 238, 144, 82, 2, 87, 146, 127, 248, 62, 133, 235, 114, 108, 71, 139, 97, 228, 25, 92, 127, 176, 2, 17, 0, 0, 0, 5, 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