Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bfd5ed886f47831080a4c092fd357b3d89d0c253b24fbd431a5b1065a201b5b

Tx prefix hash: 1397f88a49a17fcb4b128c258aefa0d94ba2c4e69133ff44b62f109b9968a234
Tx public key: b1a0c7cf82d1da6344ff6e51a5e1490dbe2b97039b9b3b27db1962939de33e72
Timestamp: 1725499922 Timestamp [UCT]: 2024-09-05 01:32:02 Age [y:d:h:m:s]: 00:080:17:14:33
Block: 1103150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57722 RingCT/type: yes/0
Extra: 01b1a0c7cf82d1da6344ff6e51a5e1490dbe2b97039b9b3b27db1962939de33e7202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f07769b7114db9620146d8a3cb76ce26af377d983babd8c92a66bae33452e1c 0.600000000000 1579867 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": 1103160, "vin": [ { "gen": { "height": 1103150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f07769b7114db9620146d8a3cb76ce26af377d983babd8c92a66bae33452e1c" } } ], "extra": [ 1, 177, 160, 199, 207, 130, 209, 218, 99, 68, 255, 110, 81, 165, 225, 73, 13, 190, 43, 151, 3, 155, 155, 59, 39, 219, 25, 98, 147, 157, 227, 62, 114, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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