Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011177f6fcb1164c38d751fd969c1b21f9b2ff1830db77de973d1101db98b19f

Tx prefix hash: cdfaed17426519e4c2dffc1e8b66bf9898b843f46e65d77c69aaf71191eaf286
Tx public key: 9b5767351d670f01bee7e6489ad4d5a67c169dcd8bea62c3094f813d31880f55
Timestamp: 1764302187 Timestamp [UCT]: 2025-11-28 03:56:27 Age [y:d:h:m:s]: 00:025:13:50:06
Block: 1421714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18306 RingCT/type: yes/0
Extra: 019b5767351d670f01bee7e6489ad4d5a67c169dcd8bea62c3094f813d31880f550211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ba2bdc1e8bba0b5c54169bbea7a3e38e064b6646ab12a3ae7df8bed4ffb21fe 0.600000000000 1910271 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": 1421724, "vin": [ { "gen": { "height": 1421714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ba2bdc1e8bba0b5c54169bbea7a3e38e064b6646ab12a3ae7df8bed4ffb21fe" } } ], "extra": [ 1, 155, 87, 103, 53, 29, 103, 15, 1, 190, 231, 230, 72, 154, 212, 213, 166, 124, 22, 157, 205, 139, 234, 98, 195, 9, 79, 129, 61, 49, 136, 15, 85, 2, 17, 0, 0, 0, 2, 78, 123, 252, 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