Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6e06f08d8cd43400203cc03fd916647cbfe85276de5856851283e15ef508531

Tx prefix hash: 757e7e79ed5c0a526b384216d8bd80e67bc7cce9e01c4e4223e1e760b3b48635
Tx public key: 02dfde713dcd6b7c867feb34f78bfe4cd8ea8ac714e54ee5945861f38e1666b6
Timestamp: 1725276608 Timestamp [UCT]: 2024-09-02 11:30:08 Age [y:d:h:m:s]: 00:083:06:31:36
Block: 1101295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59555 RingCT/type: yes/0
Extra: 0102dfde713dcd6b7c867feb34f78bfe4cd8ea8ac714e54ee5945861f38e1666b6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2c6494fbba0a0cc19291414df09561efa44dc3b024ba23dcc8b995e32f992f7 0.600000000000 1577292 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": 1101305, "vin": [ { "gen": { "height": 1101295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2c6494fbba0a0cc19291414df09561efa44dc3b024ba23dcc8b995e32f992f7" } } ], "extra": [ 1, 2, 223, 222, 113, 61, 205, 107, 124, 134, 127, 235, 52, 247, 139, 254, 76, 216, 234, 138, 199, 20, 229, 78, 229, 148, 88, 97, 243, 142, 22, 102, 182, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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