Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0744631c2a20e991aba0f585bc793a5361820abc7d6535fcddb7af48205a29

Tx prefix hash: 5bcb123c78fcbe015b517de5c508eeea91fe80dddbc23d59fa91c1449603ec9a
Tx public key: ab0b2c845f2e81d80901b71846987a8e50447f0d4c3243d13809ada1cc5914bc
Timestamp: 1702178946 Timestamp [UCT]: 2023-12-10 03:29:06 Age [y:d:h:m:s]: 01:115:20:37:07
Block: 909812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343948 RingCT/type: yes/0
Extra: 01ab0b2c845f2e81d80901b71846987a8e50447f0d4c3243d13809ada1cc5914bc0211000000084b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41aa900bc891c7e588dc8e5bba8ac2f33a9f4f6c78522ae990f5a188936a939e 0.600000000000 1366935 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": 909822, "vin": [ { "gen": { "height": 909812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41aa900bc891c7e588dc8e5bba8ac2f33a9f4f6c78522ae990f5a188936a939e" } } ], "extra": [ 1, 171, 11, 44, 132, 95, 46, 129, 216, 9, 1, 183, 24, 70, 152, 122, 142, 80, 68, 127, 13, 76, 50, 67, 209, 56, 9, 173, 161, 204, 89, 20, 188, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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