Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f216bf9d807fb014145bedfb5037ff24690fb16b4b19fe17392d35427045e6

Tx prefix hash: 45b5a1d1328adbb2130d415d31235ed72f8c7c36d1660dc76facb830a491a55b
Tx public key: b33ef296f8fb4fd3d52e12f1122caf935d698a9161fd70664012ecf4d7e06c7f
Timestamp: 1755925041 Timestamp [UCT]: 2025-08-23 04:57:21 Age [y:d:h:m:s]: 00:089:17:29:23
Block: 1352466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64064 RingCT/type: yes/0
Extra: 01b33ef296f8fb4fd3d52e12f1122caf935d698a9161fd70664012ecf4d7e06c7f0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0550e9a59829d13144032e642186f4ab0ca56eb7fec0b330b2e96bc84cd46a7 0.600000000000 1840431 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": 1352476, "vin": [ { "gen": { "height": 1352466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0550e9a59829d13144032e642186f4ab0ca56eb7fec0b330b2e96bc84cd46a7" } } ], "extra": [ 1, 179, 62, 242, 150, 248, 251, 79, 211, 213, 46, 18, 241, 18, 44, 175, 147, 93, 105, 138, 145, 97, 253, 112, 102, 64, 18, 236, 244, 215, 224, 108, 127, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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