Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eab4ffe1ae76f7a05faf0a4caf8fd8471655e4e9354eceba9849e91b4b9421af

Tx prefix hash: 4aefc93d7cc8872610ef0c1673151e02a11813396a85d9416212c77ac3ca6116
Tx public key: bdf5f8b8f40f8a32267e76af23811c344efccc39caa5d6c5bed8b62188145641
Timestamp: 1761169587 Timestamp [UCT]: 2025-10-22 21:46:27 Age [y:d:h:m:s]: 00:015:00:29:07
Block: 1395769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10736 RingCT/type: yes/0
Extra: 01bdf5f8b8f40f8a32267e76af23811c344efccc39caa5d6c5bed8b62188145641021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b07a2eaee36597b2a5d6a3c023059656404d192c0ebe0ec958cde0c67c71d9bb 0.600000000000 1884052 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": 1395779, "vin": [ { "gen": { "height": 1395769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b07a2eaee36597b2a5d6a3c023059656404d192c0ebe0ec958cde0c67c71d9bb" } } ], "extra": [ 1, 189, 245, 248, 184, 244, 15, 138, 50, 38, 126, 118, 175, 35, 129, 28, 52, 78, 252, 204, 57, 202, 165, 214, 197, 190, 216, 182, 33, 136, 20, 86, 65, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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