Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef344d25fa9a59eed5bdd9495934ce0f94524c7acd042bbf9318bd57c095df7

Tx prefix hash: e0910457617f77f4c8685e17fcfd5de7abbdd46fabd34def2883b0ce28870db2
Tx public key: a6351005405d23628c0e6a24aece1d17b7b396c9d4d6eb52c48ccb6a9c326227
Timestamp: 1768291667 Timestamp [UCT]: 2026-01-13 08:07:47 Age [y:d:h:m:s]: 00:014:16:04:33
Block: 1454630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10464 RingCT/type: yes/0
Extra: 01a6351005405d23628c0e6a24aece1d17b7b396c9d4d6eb52c48ccb6a9c32622702110000000449d73e98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35460aadbdfee3b3d14c9550b57e4cf0e6419e0904d86bda8c8b565f702df32b 0.600000000000 1943720 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": 1454640, "vin": [ { "gen": { "height": 1454630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35460aadbdfee3b3d14c9550b57e4cf0e6419e0904d86bda8c8b565f702df32b" } } ], "extra": [ 1, 166, 53, 16, 5, 64, 93, 35, 98, 140, 14, 106, 36, 174, 206, 29, 23, 183, 179, 150, 201, 212, 214, 235, 82, 196, 140, 203, 106, 156, 50, 98, 39, 2, 17, 0, 0, 0, 4, 73, 215, 62, 152, 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