Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a136efe4e441582b62eb83eb750d61854bed7943166bd70e061d844585ecf6

Tx prefix hash: c5c3222dfba7b963cd6489bd9c83bb160b7d83f5ae4b5bb97d10ce84ee05b874
Tx public key: 7ef0cf2e9baf443c74f3998c4a4a63d79fdaa0dca453530c9398ed0e07a5eab8
Timestamp: 1724662495 Timestamp [UCT]: 2024-08-26 08:54:55 Age [y:d:h:m:s]: 00:093:20:37:13
Block: 1096206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67136 RingCT/type: yes/0
Extra: 017ef0cf2e9baf443c74f3998c4a4a63d79fdaa0dca453530c9398ed0e07a5eab802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a3a48706a73856c57d35ac2848953cac9c9e2f19df2933ac76979617822139c 0.600000000000 1571393 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": 1096216, "vin": [ { "gen": { "height": 1096206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a3a48706a73856c57d35ac2848953cac9c9e2f19df2933ac76979617822139c" } } ], "extra": [ 1, 126, 240, 207, 46, 155, 175, 68, 60, 116, 243, 153, 140, 74, 74, 99, 215, 159, 218, 160, 220, 164, 83, 83, 12, 147, 152, 237, 14, 7, 165, 234, 184, 2, 17, 0, 0, 0, 1, 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