Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e706d96d4d327421d7ff4cbe4c63097e6d29b7dc1717fed1038b2061eb202ee3

Tx prefix hash: c12f5ec2021354b756a71a32fb01b9df7f56a332dba45ce486b91ed699dfec22
Tx public key: b8e2d6f2e57a9f294363f40ce93d947c718bcbad474e3d8c214b346059da655f
Timestamp: 1761776386 Timestamp [UCT]: 2025-10-29 22:19:46 Age [y:d:h:m:s]: 00:067:23:56:19
Block: 1400787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48700 RingCT/type: yes/0
Extra: 01b8e2d6f2e57a9f294363f40ce93d947c718bcbad474e3d8c214b346059da655f02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a78caa552dbdc6f0d235020b764471d5a4cedca3c3a7d398ac53dc742d3ca02b 0.600000000000 1889106 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": 1400797, "vin": [ { "gen": { "height": 1400787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78caa552dbdc6f0d235020b764471d5a4cedca3c3a7d398ac53dc742d3ca02b" } } ], "extra": [ 1, 184, 226, 214, 242, 229, 122, 159, 41, 67, 99, 244, 12, 233, 61, 148, 124, 113, 139, 203, 173, 71, 78, 61, 140, 33, 75, 52, 96, 89, 218, 101, 95, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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