Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c3c6a6e40eaa2cbc582a7028ddee13fc16e61bd777387ed5294bfbbb6cdb3bd

Tx prefix hash: 0d82ec1c8815cf2f7091b225fc80c4f66bf456f14f71c0249269454a820ee620
Tx public key: 7fa83695cef739ab5dd6aeb4dc969fe8d7317bafa00530e240a6c9421da0c88a
Timestamp: 1698553422 Timestamp [UCT]: 2023-10-29 04:23:42 Age [y:d:h:m:s]: 01:090:16:47:58
Block: 879968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325940 RingCT/type: yes/0
Extra: 017fa83695cef739ab5dd6aeb4dc969fe8d7317bafa00530e240a6c9421da0c88a02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.745247858000 dcy

stealth address amount amount idx
00: 8a862dfd91de16c875bda32fdb597fcf961eb32ee518a442fd4e341d5071b3e3 0.745247858000 1335508 of 0

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": 879978, "vin": [ { "gen": { "height": 879968 } } ], "vout": [ { "amount": 745247858, "target": { "key": "8a862dfd91de16c875bda32fdb597fcf961eb32ee518a442fd4e341d5071b3e3" } } ], "extra": [ 1, 127, 168, 54, 149, 206, 247, 57, 171, 93, 214, 174, 180, 220, 150, 159, 232, 215, 49, 123, 175, 160, 5, 48, 226, 64, 166, 201, 66, 29, 160, 200, 138, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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