Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b009bc0f399d0e24463b58e906604bf3a0e63eba47724a5a983588ac6224bb3f

Tx prefix hash: 556e3e87267fbe5c83fff5c68ae8f87546458a51a61d9777df5ec5cc9b61e49f
Tx public key: edbc7826a43d91eba8f720f26ed4fdc84b3ca32194aca0907a3bdc8ed22bf5dc
Timestamp: 1702808013 Timestamp [UCT]: 2023-12-17 10:13:33 Age [y:d:h:m:s]: 01:034:01:21:59
Block: 915027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285655 RingCT/type: yes/0
Extra: 01edbc7826a43d91eba8f720f26ed4fdc84b3ca32194aca0907a3bdc8ed22bf5dc021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11846692a43f967bc1aa9eb7e676833392d3b74a6da0ad8e45afa3b77ca51f7d 0.600000000000 1372399 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": 915037, "vin": [ { "gen": { "height": 915027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11846692a43f967bc1aa9eb7e676833392d3b74a6da0ad8e45afa3b77ca51f7d" } } ], "extra": [ 1, 237, 188, 120, 38, 164, 61, 145, 235, 168, 247, 32, 242, 110, 212, 253, 200, 75, 60, 163, 33, 148, 172, 160, 144, 122, 59, 220, 142, 210, 43, 245, 220, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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