Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9f0cc89f2baebb96e7cc5f4606b573064dc6007628abd479e3836e4aec07d4

Tx prefix hash: a49f49a6067feea6604f3db78c62002d24f6dd70686925d8f763ce6f6eb91997
Tx public key: 4d633738ad24f1fa42a1471fbf0868ec380918f0d6c088b0e9234f404dd24d85
Timestamp: 1581156675 Timestamp [UCT]: 2020-02-08 10:11:15 Age [y:d:h:m:s]: 04:292:20:35:45
Block: 60834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101112 RingCT/type: yes/0
Extra: 014d633738ad24f1fa42a1471fbf0868ec380918f0d6c088b0e9234f404dd24d850211000000064943cd9f000000000000000000

1 output(s) for total of 385.869113753000 dcy

stealth address amount amount idx
00: ac1aedd5c53ecebf46c635fb762eff0f5d60f79f78d1ace712a3d44906e01adc 385.869113753000 112085 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": 60844, "vin": [ { "gen": { "height": 60834 } } ], "vout": [ { "amount": 385869113753, "target": { "key": "ac1aedd5c53ecebf46c635fb762eff0f5d60f79f78d1ace712a3d44906e01adc" } } ], "extra": [ 1, 77, 99, 55, 56, 173, 36, 241, 250, 66, 161, 71, 31, 191, 8, 104, 236, 56, 9, 24, 240, 214, 192, 136, 176, 233, 35, 79, 64, 77, 210, 77, 133, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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