Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb18cf76d6e686ad8e61c4c97a36521d3580aa1f6af2020698c21c2f136b418e

Tx prefix hash: d3e685c1815b7426d94025c3a0fb363972a087a56736938ddc88ded2951bcf1c
Tx public key: aaa0d0e65a7f15b14933f9d2f2ba4730bde719bd6979a43f38e7ac050b74e1da
Timestamp: 1762710937 Timestamp [UCT]: 2025-11-09 17:55:37 Age [y:d:h:m:s]: 00:057:06:32:23
Block: 1408531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41022 RingCT/type: yes/0
Extra: 01aaa0d0e65a7f15b14933f9d2f2ba4730bde719bd6979a43f38e7ac050b74e1da021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b986e820ac367df92cc52f4acbe93d8de0ee939f91a106de9782a66c391e7c 0.600000000000 1896960 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": 1408541, "vin": [ { "gen": { "height": 1408531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b986e820ac367df92cc52f4acbe93d8de0ee939f91a106de9782a66c391e7c" } } ], "extra": [ 1, 170, 160, 208, 230, 90, 127, 21, 177, 73, 51, 249, 210, 242, 186, 71, 48, 189, 231, 25, 189, 105, 121, 164, 63, 56, 231, 172, 5, 11, 116, 225, 218, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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