Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0293c4465ed1f216850a9965f0a70a8e6a4d4287fd92fa6d03f95cf5339240

Tx prefix hash: 81abc03e8751b98f08aaf21be753c7ab55d665bb82fbdfdd745247bb4e538aca
Tx public key: ab368b8ce1c424ada5c75b7a663e73ef216f0a24a27b011dc37c8fc513411ab1
Timestamp: 1707866263 Timestamp [UCT]: 2024-02-13 23:17:43 Age [y:d:h:m:s]: 01:268:21:49:32
Block: 956957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450948 RingCT/type: yes/0
Extra: 01ab368b8ce1c424ada5c75b7a663e73ef216f0a24a27b011dc37c8fc513411ab10211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d9a02b342eb8f906c0f5fa5bb6e1057bbd9a4a22ea95670a023e3f27143f74 0.600000000000 1416271 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": 956967, "vin": [ { "gen": { "height": 956957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d9a02b342eb8f906c0f5fa5bb6e1057bbd9a4a22ea95670a023e3f27143f74" } } ], "extra": [ 1, 171, 54, 139, 140, 225, 196, 36, 173, 165, 199, 91, 122, 102, 62, 115, 239, 33, 111, 10, 36, 162, 123, 1, 29, 195, 124, 143, 197, 19, 65, 26, 177, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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