Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd5aa5a1ead1dfa39bad85eb9ca24d20714d1cab6d006c37b6b811a5435b596

Tx prefix hash: dbd68c8bb01a9993584024518814438951434393217201cb28b29c19d5fd139d
Tx public key: fafd249c50cf7ec1c09ae8bfd493070a7100d5377a803125292f03b9350ed65d
Timestamp: 1708075888 Timestamp [UCT]: 2024-02-16 09:31:28 Age [y:d:h:m:s]: 01:048:15:53:54
Block: 958690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295814 RingCT/type: yes/0
Extra: 01fafd249c50cf7ec1c09ae8bfd493070a7100d5377a803125292f03b9350ed65d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36976e984b94326c2ef2df3e4ad1922e4bd5d9719241b47ede0d3dd27fc3b20b 0.600000000000 1418051 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": 958700, "vin": [ { "gen": { "height": 958690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36976e984b94326c2ef2df3e4ad1922e4bd5d9719241b47ede0d3dd27fc3b20b" } } ], "extra": [ 1, 250, 253, 36, 156, 80, 207, 126, 193, 192, 154, 232, 191, 212, 147, 7, 10, 113, 0, 213, 55, 122, 128, 49, 37, 41, 47, 3, 185, 53, 14, 214, 93, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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