Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 195872521a10795d8c4c662f8e315795d1bf26d10b9e57eabfb5881cbede2fb3

Tx prefix hash: 2a00e8436aeba93f9b1951524716c60caae6bbc3bd3c05d6da4b04ae997b913b
Tx public key: 348ae15698e539bf841118bf55d44a750d09a2e2dcd189d61712423acb895280
Timestamp: 1579038924 Timestamp [UCT]: 2020-01-14 21:55:24 Age [y:d:h:m:s]: 04:347:11:45:31
Block: 45624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137882 RingCT/type: yes/0
Extra: 01348ae15698e539bf841118bf55d44a750d09a2e2dcd189d61712423acb895280021100000003d81c26c0000000000000000000

1 output(s) for total of 433.348267204000 dcy

stealth address amount amount idx
00: df0a03ca2f70a1a987032f31302f19d65fc24669ff8e7758e2b3bcab4dfdf07c 433.348267204000 83460 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": 45634, "vin": [ { "gen": { "height": 45624 } } ], "vout": [ { "amount": 433348267204, "target": { "key": "df0a03ca2f70a1a987032f31302f19d65fc24669ff8e7758e2b3bcab4dfdf07c" } } ], "extra": [ 1, 52, 138, 225, 86, 152, 229, 57, 191, 132, 17, 24, 191, 85, 212, 74, 117, 13, 9, 162, 226, 220, 209, 137, 214, 23, 18, 66, 58, 203, 137, 82, 128, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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