Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0daffb797a688b1ee5305a7ac5727edf8d5fb3850b1a4170191b6091b36f142d

Tx prefix hash: 44221dcb103db257119ca75f52d7cf27da89c7d0e36edd6f36e3e6d71b1dbbcf
Tx public key: 1d9883b91c0f2378ec73f24208f16eed0439d3958aa07b32c566c1f1b59905d5
Timestamp: 1706838919 Timestamp [UCT]: 2024-02-02 01:55:19 Age [y:d:h:m:s]: 01:099:00:18:07
Block: 948434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331847 RingCT/type: yes/0
Extra: 011d9883b91c0f2378ec73f24208f16eed0439d3958aa07b32c566c1f1b59905d502110000000510a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a603aec617baea50ea22f5ea04cca09fedbb4a6838bb61e10b86b9027fe312 0.600000000000 1406842 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": 948444, "vin": [ { "gen": { "height": 948434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a603aec617baea50ea22f5ea04cca09fedbb4a6838bb61e10b86b9027fe312" } } ], "extra": [ 1, 29, 152, 131, 185, 28, 15, 35, 120, 236, 115, 242, 66, 8, 241, 110, 237, 4, 57, 211, 149, 138, 160, 123, 50, 197, 102, 193, 241, 181, 153, 5, 213, 2, 17, 0, 0, 0, 5, 16, 161, 116, 143, 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