Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49cbb770c5b394172f6bfcec05ec54e38a1d467404c4d31e3448a5e121955bc5

Tx prefix hash: ccfe52003687661613f8b4a898c79a9370dc8a5046379c1bacce72446a2579bb
Tx public key: 66b62ccf052c2d3b6fac8290eceae1461914c6c647f4430278e2e6c3ca6fca06
Timestamp: 1578947185 Timestamp [UCT]: 2020-01-13 20:26:25 Age [y:d:h:m:s]: 04:347:18:37:27
Block: 44941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138007 RingCT/type: yes/0
Extra: 0166b62ccf052c2d3b6fac8290eceae1461914c6c647f4430278e2e6c3ca6fca060211000000174943cd9f000000000000000000

1 output(s) for total of 435.661874811000 dcy

stealth address amount amount idx
00: bb66e35f8e9867ed4955ab973f49317f4e82a9ea618d021ade1e3192a898e6b7 435.661874811000 81951 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": 44951, "vin": [ { "gen": { "height": 44941 } } ], "vout": [ { "amount": 435661874811, "target": { "key": "bb66e35f8e9867ed4955ab973f49317f4e82a9ea618d021ade1e3192a898e6b7" } } ], "extra": [ 1, 102, 182, 44, 207, 5, 44, 45, 59, 111, 172, 130, 144, 236, 234, 225, 70, 25, 20, 198, 198, 71, 244, 67, 2, 120, 226, 230, 195, 202, 111, 202, 6, 2, 17, 0, 0, 0, 23, 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