Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb649fdbbe4c1b3685cef5aae120be7f9a3ea0c4f6c0f71fd977ca3540d7815

Tx prefix hash: f3d2d10aaa5e5b88012f9494c36862887066acba44a768dbcb610eeb41914059
Tx public key: 559f0f7b34677c726b879530de01a97d444336dfa6d45d4e4bbfaced62e72554
Timestamp: 1761257745 Timestamp [UCT]: 2025-10-23 22:15:45 Age [y:d:h:m:s]: 00:099:03:52:07
Block: 1396498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70804 RingCT/type: yes/0
Extra: 01559f0f7b34677c726b879530de01a97d444336dfa6d45d4e4bbfaced62e72554021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b585177e3e5749cbe6b164341143a6eb0aba7a7f85826433f03ae2be9e5d3621 0.600000000000 1884785 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": 1396508, "vin": [ { "gen": { "height": 1396498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b585177e3e5749cbe6b164341143a6eb0aba7a7f85826433f03ae2be9e5d3621" } } ], "extra": [ 1, 85, 159, 15, 123, 52, 103, 124, 114, 107, 135, 149, 48, 222, 1, 169, 125, 68, 67, 54, 223, 166, 212, 93, 78, 75, 191, 172, 237, 98, 231, 37, 84, 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