Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97c351f36b7ad9a9c881c890bc799d54e68fd2644ddb3b57b687c934dd021fa5

Tx prefix hash: fad7c121a4e382ac606ea7357dad8f7137a4d8260a0bafda37222e0ae6f2cbfe
Tx public key: d0e0a190637936e2be03c472c7236b08e6c256497cdb9ffd805e02db6de85f5e
Timestamp: 1729281071 Timestamp [UCT]: 2024-10-18 19:51:11 Age [y:d:h:m:s]: 01:033:10:12:39
Block: 1134505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282241 RingCT/type: yes/0
Extra: 01d0e0a190637936e2be03c472c7236b08e6c256497cdb9ffd805e02db6de85f5e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c76cd2ee4a48d2d3edcd7a24dbb38ff1345e023170f3427dbb36a048574387c9 0.600000000000 1617818 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": 1134515, "vin": [ { "gen": { "height": 1134505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c76cd2ee4a48d2d3edcd7a24dbb38ff1345e023170f3427dbb36a048574387c9" } } ], "extra": [ 1, 208, 224, 161, 144, 99, 121, 54, 226, 190, 3, 196, 114, 199, 35, 107, 8, 230, 194, 86, 73, 124, 219, 159, 253, 128, 94, 2, 219, 109, 232, 95, 94, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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