Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc605a816cef74f06c71e237bad1c457ce06472153140db2cb706b1cc86a72b8

Tx prefix hash: d96823141a6f594c02685a54503734606790df3e351b7dfb44a2b13d382907c1
Tx public key: 9b77bbe5cb16b907a2c7435d078bc2a8171c70dd7500fcda55d8525dd02e6210
Timestamp: 1728293516 Timestamp [UCT]: 2024-10-07 09:31:56 Age [y:d:h:m:s]: 00:209:01:42:08
Block: 1126310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149232 RingCT/type: yes/0
Extra: 019b77bbe5cb16b907a2c7435d078bc2a8171c70dd7500fcda55d8525dd02e621002110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e2c0b5effa760254a4556e828c23801212b46d4c1d0e93a269fe7741e0c2af9 0.600000000000 1609099 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": 1126320, "vin": [ { "gen": { "height": 1126310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e2c0b5effa760254a4556e828c23801212b46d4c1d0e93a269fe7741e0c2af9" } } ], "extra": [ 1, 155, 119, 187, 229, 203, 22, 185, 7, 162, 199, 67, 93, 7, 139, 194, 168, 23, 28, 112, 221, 117, 0, 252, 218, 85, 216, 82, 93, 208, 46, 98, 16, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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