Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb1de81857a1931eb17da958d1d3672914557422d19620a4fabe4ea092d53e2

Tx prefix hash: c6581e36b519c668dfcd44b8c896f1825a0ef582bb11e4737e4ff2e11450491e
Tx public key: 7289ef34ceac51eb6edb6226ba6a6bcae6f36e10df7fdc8e57633dfb96b94f01
Timestamp: 1676236300 Timestamp [UCT]: 2023-02-12 21:11:40 Age [y:d:h:m:s]: 02:077:19:48:27
Block: 695623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577229 RingCT/type: yes/0
Extra: 017289ef34ceac51eb6edb6226ba6a6bcae6f36e10df7fdc8e57633dfb96b94f010211000000045029cbac000000000000000000

1 output(s) for total of 3.041670417000 dcy

stealth address amount amount idx
00: 63e21d99fc13cacd9e9535bb037ad4747c60b68e94e8a1edadadd197133fda4f 3.041670417000 1138580 of 0

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": 695633, "vin": [ { "gen": { "height": 695623 } } ], "vout": [ { "amount": 3041670417, "target": { "key": "63e21d99fc13cacd9e9535bb037ad4747c60b68e94e8a1edadadd197133fda4f" } } ], "extra": [ 1, 114, 137, 239, 52, 206, 172, 81, 235, 110, 219, 98, 38, 186, 106, 107, 202, 230, 243, 110, 16, 223, 127, 220, 142, 87, 99, 61, 251, 150, 185, 79, 1, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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