Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9395624531ec862f737cc2214e7ba7a0ab88a3f6f1fe0b771d961c1a04ebbb3

Tx prefix hash: 945f9609b67f615d0c8ade920e77d573644282128b2b0d89627fc60b28fef8d1
Tx public key: d53757cca9aea80f6f08dba3854ff1b0ccc8cfdbf6de92cffa85ee428b4c2861
Timestamp: 1706593492 Timestamp [UCT]: 2024-01-30 05:44:52 Age [y:d:h:m:s]: 01:067:23:56:01
Block: 946383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309668 RingCT/type: yes/0
Extra: 01d53757cca9aea80f6f08dba3854ff1b0ccc8cfdbf6de92cffa85ee428b4c286102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f78a5d5615a6042f680dbaf0dda6ccf07ea90693aefa8bbe8a4165371a46c8 0.600000000000 1404715 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": 946393, "vin": [ { "gen": { "height": 946383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f78a5d5615a6042f680dbaf0dda6ccf07ea90693aefa8bbe8a4165371a46c8" } } ], "extra": [ 1, 213, 55, 87, 204, 169, 174, 168, 15, 111, 8, 219, 163, 133, 79, 241, 176, 204, 200, 207, 219, 246, 222, 146, 207, 250, 133, 238, 66, 139, 76, 40, 97, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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