Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e31981e1df1c9a4e99da9b2b1cc51847100a8baac3bd098a0fbd494d7629134

Tx prefix hash: 5e21ac5d20ddb98c23467d3c2461ff2fc3b50ba1f36212dec163fe830ae186ee
Tx public key: 3d705ae51161ce409895529a96278635374a395760a7b10aaf67ca5a58c5f98d
Timestamp: 1709274862 Timestamp [UCT]: 2024-03-01 06:34:22 Age [y:d:h:m:s]: 01:049:02:10:40
Block: 968649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296096 RingCT/type: yes/0
Extra: 013d705ae51161ce409895529a96278635374a395760a7b10aaf67ca5a58c5f98d0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e3a75acd66d56fae014d65d7f4c911b925afb1b8072c3fb324ecd33e43768b7 0.600000000000 1428466 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": 968659, "vin": [ { "gen": { "height": 968649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e3a75acd66d56fae014d65d7f4c911b925afb1b8072c3fb324ecd33e43768b7" } } ], "extra": [ 1, 61, 112, 90, 229, 17, 97, 206, 64, 152, 149, 82, 154, 150, 39, 134, 53, 55, 74, 57, 87, 96, 167, 177, 10, 175, 103, 202, 90, 88, 197, 249, 141, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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