Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81a74352aea44e4518d2ab896af0fc22c9e964fff86bb93a5cd82742c494acef

Tx prefix hash: ab294b231d3a1dc30fa03a204aa4dfb81bb715ec96e558ba97da63ed7f1f2039
Tx public key: b2debc1d02aa9439ef42f5db07b5ae59722c60ec7167c19ed2b7aab3a55310ca
Timestamp: 1749418418 Timestamp [UCT]: 2025-06-08 21:33:38 Age [y:d:h:m:s]: 00:155:10:37:13
Block: 1300896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108769 RingCT/type: yes/0
Extra: 01b2debc1d02aa9439ef42f5db07b5ae59722c60ec7167c19ed2b7aab3a55310ca021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c61bc2a36bc6edab9f72172d4e53cb4b3714ed626f77f6400322097494da9a9 0.600000000000 1788449 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": 1300906, "vin": [ { "gen": { "height": 1300896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c61bc2a36bc6edab9f72172d4e53cb4b3714ed626f77f6400322097494da9a9" } } ], "extra": [ 1, 178, 222, 188, 29, 2, 170, 148, 57, 239, 66, 245, 219, 7, 181, 174, 89, 114, 44, 96, 236, 113, 103, 193, 158, 210, 183, 170, 179, 165, 83, 16, 202, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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