Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5f62be7aecea1a822299283f7c16e8a0bbab46a451a8e635c5199be1bf9edc

Tx prefix hash: 86237fb6bde42f20fa91be06a171f7dc31fa320ffccab0248dac144fd5660d68
Tx public key: 2e87a596b6dfac38088fd0f8415415f929c62cfe44a32818515d8840f40d8b63
Timestamp: 1737567360 Timestamp [UCT]: 2025-01-22 17:36:00 Age [y:d:h:m:s]: 00:147:08:25:40
Block: 1203004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105032 RingCT/type: yes/0
Extra: 012e87a596b6dfac38088fd0f8415415f929c62cfe44a32818515d8840f40d8b63021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fbb92338ee883e60be2482b84f650808c971831971c4c3a1ef7d1f5cfb0e848 0.600000000000 1689675 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": 1203014, "vin": [ { "gen": { "height": 1203004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fbb92338ee883e60be2482b84f650808c971831971c4c3a1ef7d1f5cfb0e848" } } ], "extra": [ 1, 46, 135, 165, 150, 182, 223, 172, 56, 8, 143, 208, 248, 65, 84, 21, 249, 41, 198, 44, 254, 68, 163, 40, 24, 81, 93, 136, 64, 244, 13, 139, 99, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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