Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed729ba3eb6a032071301b3fa21c5c9a8fa93f35c9cf902b21e3a612057ed9f7

Tx prefix hash: 5450a9419dab22f1233cc37e22442225fbaae83f518181d997313f2f1e3aeae7
Tx public key: ffbdfea95755b05c2950ae54e5684d51e33d1987cc31859ef2fdbec6b74c803c
Timestamp: 1724571424 Timestamp [UCT]: 2024-08-25 07:37:04 Age [y:d:h:m:s]: 00:095:02:59:30
Block: 1095454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68041 RingCT/type: yes/0
Extra: 01ffbdfea95755b05c2950ae54e5684d51e33d1987cc31859ef2fdbec6b74c803c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0f8cdc8598163c55d8ed6b9f6ee5d4d88c08f29adbd6a26f3f826dbfe2f7825 0.600000000000 1570629 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": 1095464, "vin": [ { "gen": { "height": 1095454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0f8cdc8598163c55d8ed6b9f6ee5d4d88c08f29adbd6a26f3f826dbfe2f7825" } } ], "extra": [ 1, 255, 189, 254, 169, 87, 85, 176, 92, 41, 80, 174, 84, 229, 104, 77, 81, 227, 61, 25, 135, 204, 49, 133, 158, 242, 253, 190, 198, 183, 76, 128, 60, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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