Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62e638008a6eef29124c3381e448e42236c70ab04f8c0db1f0be197c0f50aca7

Tx prefix hash: 50b15dbc71b74fac5382e6c73b109c9a1426a170b6255b1698a87e7bf18d8818
Tx public key: 6c6176c1d325bfe36f8bdd0de00554a2eedf1273ef4adaa5984a3f902397cb22
Timestamp: 1710385483 Timestamp [UCT]: 2024-03-14 03:04:43 Age [y:d:h:m:s]: 01:300:00:57:40
Block: 977859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473212 RingCT/type: yes/0
Extra: 016c6176c1d325bfe36f8bdd0de00554a2eedf1273ef4adaa5984a3f902397cb220211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f9e3ee10f3f989373ad0a514311bcf95266264867d8bd6e87fb952c83f9054c 0.600000000000 1437866 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": 977869, "vin": [ { "gen": { "height": 977859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f9e3ee10f3f989373ad0a514311bcf95266264867d8bd6e87fb952c83f9054c" } } ], "extra": [ 1, 108, 97, 118, 193, 211, 37, 191, 227, 111, 139, 221, 13, 224, 5, 84, 162, 238, 223, 18, 115, 239, 74, 218, 165, 152, 74, 63, 144, 35, 151, 203, 34, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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