Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2937f1f5af225aef68696a6b5fd8c23c909f1b3bdc1c5e90b56c3624cabb3878

Tx prefix hash: 69c7673bfe3b16bde0d9805312af94b0eb066d4cc133cab713385b8162ba158b
Tx public key: bfc862a776e8428d801adbd92e871e47d77ddd158d100eed9caaedd6ac0ff943
Timestamp: 1581232152 Timestamp [UCT]: 2020-02-09 07:09:12 Age [y:d:h:m:s]: 04:323:04:49:29
Block: 61096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123179 RingCT/type: yes/0
Extra: 01bfc862a776e8428d801adbd92e871e47d77ddd158d100eed9caaedd6ac0ff9430211000000154ac5aa02000000000000000000

1 output(s) for total of 385.091920194000 dcy

stealth address amount amount idx
00: b3d993735ba950e6fa4168a86f8df444bbd0d209b73834a6ab73c08e0959be4e 385.091920194000 112603 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": 61106, "vin": [ { "gen": { "height": 61096 } } ], "vout": [ { "amount": 385091920194, "target": { "key": "b3d993735ba950e6fa4168a86f8df444bbd0d209b73834a6ab73c08e0959be4e" } } ], "extra": [ 1, 191, 200, 98, 167, 118, 232, 66, 141, 128, 26, 219, 217, 46, 135, 30, 71, 215, 125, 221, 21, 141, 16, 14, 237, 156, 170, 237, 214, 172, 15, 249, 67, 2, 17, 0, 0, 0, 21, 74, 197, 170, 2, 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