Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bdaa20bbee1f210ffa20d4cd69732501ffbb0c0c1deaa4b4b5d85fc9bcb014

Tx prefix hash: 1224a906ce7f94678b6f2338baa8630e9bf76fce303343451669e9ec12a99d89
Tx public key: 96fed0fb6f4731071e514753f32da3e5b32d86c486c0622e65b7bc2f8210d847
Timestamp: 1761685473 Timestamp [UCT]: 2025-10-28 21:04:33 Age [y:d:h:m:s]: 00:021:17:08:01
Block: 1400038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15533 RingCT/type: yes/0
Extra: 0196fed0fb6f4731071e514753f32da3e5b32d86c486c0622e65b7bc2f8210d84702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38c208d2f7ffb1f24cd9d905ad143e90d5e8e6955df7d03bb3e7a87ba744dcb 0.600000000000 1888345 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": 1400048, "vin": [ { "gen": { "height": 1400038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38c208d2f7ffb1f24cd9d905ad143e90d5e8e6955df7d03bb3e7a87ba744dcb" } } ], "extra": [ 1, 150, 254, 208, 251, 111, 71, 49, 7, 30, 81, 71, 83, 243, 45, 163, 229, 179, 45, 134, 196, 134, 192, 98, 46, 101, 183, 188, 47, 130, 16, 216, 71, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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