Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2db1f1a69a2c68a7bf43a7f5b7b3ff0a843f1a09538de81f71cd155cd4da84c3

Tx prefix hash: 80090403d90049310ce6acf4887799004b36a3756f9abc5853636ed6e2407e4c
Tx public key: 80e660cb3fea9bdd97357088958fc1cb467cb9012cd99292414a1a92a1fabfc2
Timestamp: 1740567109 Timestamp [UCT]: 2025-02-26 10:51:49 Age [y:d:h:m:s]: 00:334:09:08:46
Block: 1227598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236658 RingCT/type: yes/0
Extra: 0180e660cb3fea9bdd97357088958fc1cb467cb9012cd99292414a1a92a1fabfc2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02d217b98b883ca8f0f2e11f43360e97c3cd4b5d75be8de6d7856ec39f7fa12 0.600000000000 1714473 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": 1227608, "vin": [ { "gen": { "height": 1227598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02d217b98b883ca8f0f2e11f43360e97c3cd4b5d75be8de6d7856ec39f7fa12" } } ], "extra": [ 1, 128, 230, 96, 203, 63, 234, 155, 221, 151, 53, 112, 136, 149, 143, 193, 203, 70, 124, 185, 1, 44, 217, 146, 146, 65, 74, 26, 146, 161, 250, 191, 194, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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