Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57916961e2ca8a103e2fc35af445078da4ebc4bb8ea4d7095240881a22f6ce7

Tx prefix hash: 98cfad343e7a8fa35607b7e328854e268b52f626710a3217480229392517ff9f
Tx public key: 8359b70c9d72494c981bc4b154e59d764f7ba96cb704c7181890831f1c8596eb
Timestamp: 1638136441 Timestamp [UCT]: 2021-11-28 21:54:01 Age [y:d:h:m:s]: 03:041:13:55:54
Block: 384232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 808629 RingCT/type: yes/0
Extra: 018359b70c9d72494c981bc4b154e59d764f7ba96cb704c7181890831f1c8596eb021100000001e9564d6f000000000000000000

1 output(s) for total of 32.725045288000 dcy

stealth address amount amount idx
00: 30681b727d23d34e21e98ea412f2de2121c5deb6aed55d3aad4cc4113a1b8f2d 32.725045288000 775579 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": 384242, "vin": [ { "gen": { "height": 384232 } } ], "vout": [ { "amount": 32725045288, "target": { "key": "30681b727d23d34e21e98ea412f2de2121c5deb6aed55d3aad4cc4113a1b8f2d" } } ], "extra": [ 1, 131, 89, 183, 12, 157, 114, 73, 76, 152, 27, 196, 177, 84, 229, 157, 118, 79, 123, 169, 108, 183, 4, 199, 24, 24, 144, 131, 31, 28, 133, 150, 235, 2, 17, 0, 0, 0, 1, 233, 86, 77, 111, 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