Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e6d91ad2f7fe46b5cd381b8b7dcdb3bb392a5921692149835b45dbfa1cae5bc

Tx prefix hash: b6d51c9667f87a588085e678e4e06823a9558b2711341b2bd6d3e4063c6ddb73
Tx public key: 0fc8061da038da9175c1ecc4b2356846694d7c7c24c8e733bb4e6f35fa6ec7bf
Timestamp: 1719645537 Timestamp [UCT]: 2024-06-29 07:18:57 Age [y:d:h:m:s]: 01:139:05:21:09
Block: 1054615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358046 RingCT/type: yes/0
Extra: 010fc8061da038da9175c1ecc4b2356846694d7c7c24c8e733bb4e6f35fa6ec7bf0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c28ffbe6237b67f1281f6eb71ca804dc70c239b6316a5634c2337a66176312de 0.600000000000 1524982 of 15

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": 1054625, "vin": [ { "gen": { "height": 1054615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c28ffbe6237b67f1281f6eb71ca804dc70c239b6316a5634c2337a66176312de" } } ], "extra": [ 1, 15, 200, 6, 29, 160, 56, 218, 145, 117, 193, 236, 196, 178, 53, 104, 70, 105, 77, 124, 124, 36, 200, 231, 51, 187, 78, 111, 53, 250, 110, 199, 191, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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