Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b6f3349605e3727d508935c641a8e8e477d533aa98b00266ed4e099b9e4c2f

Tx prefix hash: 32d9957d570df263c8b3215beb3cbc392a2ba20e7d94d9e226d36a4b2fbf23c9
Tx public key: 49c0efe35f9e0bd90d507b8cc7e58dc4e6d4b647daafb20f0c8980d85596a3d8
Timestamp: 1740958256 Timestamp [UCT]: 2025-03-02 23:30:56 Age [y:d:h:m:s]: 00:256:08:14:09
Block: 1230845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180964 RingCT/type: yes/0
Extra: 0149c0efe35f9e0bd90d507b8cc7e58dc4e6d4b647daafb20f0c8980d85596a3d80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d2d6b979b3dfdc6acc94ac5f185600a6669649ba9e2777c795a259f77b11107 0.600000000000 1717748 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": 1230855, "vin": [ { "gen": { "height": 1230845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d2d6b979b3dfdc6acc94ac5f185600a6669649ba9e2777c795a259f77b11107" } } ], "extra": [ 1, 73, 192, 239, 227, 95, 158, 11, 217, 13, 80, 123, 140, 199, 229, 141, 196, 230, 212, 182, 71, 218, 175, 178, 15, 12, 137, 128, 216, 85, 150, 163, 216, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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