Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b891617123d3f392c5cc459a030ab31c9b081a480f6173b3fae2fb5dc32609

Tx prefix hash: e7a053ff26f66c7cf9f89ca21549b42830f7aa1355c2cddb8a1d7c3940f70a73
Tx public key: 3635d4c5d5feff80f0bef8b724acbda3081d93004f5d9804cf4bdc82889a1637
Timestamp: 1705041319 Timestamp [UCT]: 2024-01-12 06:35:19 Age [y:d:h:m:s]: 01:132:01:43:23
Block: 933514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355553 RingCT/type: yes/0
Extra: 013635d4c5d5feff80f0bef8b724acbda3081d93004f5d9804cf4bdc82889a163702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99da2e69b6f85b0b60ff661a61858356baf5beb2a2732c1ce371535f756bc379 0.600000000000 1391476 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": 933524, "vin": [ { "gen": { "height": 933514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99da2e69b6f85b0b60ff661a61858356baf5beb2a2732c1ce371535f756bc379" } } ], "extra": [ 1, 54, 53, 212, 197, 213, 254, 255, 128, 240, 190, 248, 183, 36, 172, 189, 163, 8, 29, 147, 0, 79, 93, 152, 4, 207, 75, 220, 130, 136, 154, 22, 55, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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