Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d93b24c9198b622f564c7e5b5c870020968b517856614b617f432aef88d7108e

Tx prefix hash: 26b5612ea611a182a02eb259f1337e20044389e55da8a16dd23d6c8d27c8d8c8
Tx public key: a9e921ca408ec58f422d5b2c0d66f2e3c3bd81b5b9b3ceb73c9ddcb6a68cbcb8
Timestamp: 1723286282 Timestamp [UCT]: 2024-08-10 10:38:02 Age [y:d:h:m:s]: 01:085:21:16:27
Block: 1084810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319840 RingCT/type: yes/0
Extra: 01a9e921ca408ec58f422d5b2c0d66f2e3c3bd81b5b9b3ceb73c9ddcb6a68cbcb8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43e9973791ad593f33d57995689373069a4ef78aa8b121dc34002781bb4255ff 0.600000000000 1559217 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": 1084820, "vin": [ { "gen": { "height": 1084810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43e9973791ad593f33d57995689373069a4ef78aa8b121dc34002781bb4255ff" } } ], "extra": [ 1, 169, 233, 33, 202, 64, 142, 197, 143, 66, 45, 91, 44, 13, 102, 242, 227, 195, 189, 129, 181, 185, 179, 206, 183, 60, 157, 220, 182, 166, 140, 188, 184, 2, 17, 0, 0, 0, 7, 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