Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bc58736cfba15a6506635bdf36f85091b2f365e5848eddffe1edc1a41a2dd6a

Tx prefix hash: e8e1dd262c0ecbfeb7ebca4ec71d2e3549a676828afcd8fb45ef038fd57b800e
Tx public key: 89dda14a170e053e1cf1bc70acc4e03f72822def6d6516fd791b014b6a3a8f20
Timestamp: 1761321108 Timestamp [UCT]: 2025-10-24 15:51:48 Age [y:d:h:m:s]: 00:097:00:44:54
Block: 1397026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69278 RingCT/type: yes/0
Extra: 0189dda14a170e053e1cf1bc70acc4e03f72822def6d6516fd791b014b6a3a8f20021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45f9ecdc805344529b5ce7600e988950d14ccb67dbd3e19b1cd6b6da8062945e 0.600000000000 1885317 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": 1397036, "vin": [ { "gen": { "height": 1397026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45f9ecdc805344529b5ce7600e988950d14ccb67dbd3e19b1cd6b6da8062945e" } } ], "extra": [ 1, 137, 221, 161, 74, 23, 14, 5, 62, 28, 241, 188, 112, 172, 196, 224, 63, 114, 130, 45, 239, 109, 101, 22, 253, 121, 27, 1, 75, 106, 58, 143, 32, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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