Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a54c3060045dd9c8a0f0f4e3649023acd64a802605faf69a945621d0f4db146e

Tx prefix hash: 0ec0368b55f6719ea65c8f98ff90172b096dc9a9a68a71d58c5a57e73a46d5dd
Tx public key: d2efddae0e31bd235bdbaa12c159f904d5a23bc5acf22e83ac23c2d63960ff30
Timestamp: 1737029952 Timestamp [UCT]: 2025-01-16 12:19:12 Age [y:d:h:m:s]: 00:157:07:40:19
Block: 1198590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112055 RingCT/type: yes/0
Extra: 01d2efddae0e31bd235bdbaa12c159f904d5a23bc5acf22e83ac23c2d63960ff30021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54d2941b47b138a80cdce616056d2b917b214a3bb2a9a24f766b4edcdb52c1a6 0.600000000000 1685215 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": 1198600, "vin": [ { "gen": { "height": 1198590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d2941b47b138a80cdce616056d2b917b214a3bb2a9a24f766b4edcdb52c1a6" } } ], "extra": [ 1, 210, 239, 221, 174, 14, 49, 189, 35, 91, 219, 170, 18, 193, 89, 249, 4, 213, 162, 59, 197, 172, 242, 46, 131, 172, 35, 194, 214, 57, 96, 255, 48, 2, 17, 0, 0, 0, 1, 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