Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83bac0923aa379c7e573cd98db5ef11d2baa373512ed6a4d0a6e581a73d8feec

Tx prefix hash: 0650889311198b21f04eb459b4268728a0bb9b92450046d5ab840e5566e0dc49
Tx public key: 14c05149f2d6be13caa4b4ce5db3b27513b6d2fab21aa7a99597d7f544e358ae
Timestamp: 1750435039 Timestamp [UCT]: 2025-06-20 15:57:19 Age [y:d:h:m:s]: 00:221:10:13:25
Block: 1309149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156005 RingCT/type: yes/0
Extra: 0114c05149f2d6be13caa4b4ce5db3b27513b6d2fab21aa7a99597d7f544e358ae021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 426e8f6a57b324c2651a84f4d1676913943304779003c71d46dfbb7684095ee0 0.600000000000 1796764 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": 1309159, "vin": [ { "gen": { "height": 1309149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "426e8f6a57b324c2651a84f4d1676913943304779003c71d46dfbb7684095ee0" } } ], "extra": [ 1, 20, 192, 81, 73, 242, 214, 190, 19, 202, 164, 180, 206, 93, 179, 178, 117, 19, 182, 210, 250, 178, 26, 167, 169, 149, 151, 215, 245, 68, 227, 88, 174, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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