Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f23d8a71200141f7752ef833409846a7419fff546dca19974fd9645f0516a9b

Tx prefix hash: 1fcfb7be7bf9010cbd672afe08fa73249dfcc9cad4d5795ed3aa824f47ed9e05
Tx public key: d652bb6e0dabe6a47d610799927a1f34b984264ab54c1c6b994f3f7abe324b81
Timestamp: 1696057017 Timestamp [UCT]: 2023-09-30 06:56:57 Age [y:d:h:m:s]: 01:260:03:07:38
Block: 859260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446902 RingCT/type: yes/0
Extra: 01d652bb6e0dabe6a47d610799927a1f34b984264ab54c1c6b994f3f7abe324b81021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.872800462000 dcy

stealth address amount amount idx
00: 88c6ca76dc17758ef7250c850be781a12653a9f6029abff9108a4597ba24a2ab 0.872800462000 1313476 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": 859270, "vin": [ { "gen": { "height": 859260 } } ], "vout": [ { "amount": 872800462, "target": { "key": "88c6ca76dc17758ef7250c850be781a12653a9f6029abff9108a4597ba24a2ab" } } ], "extra": [ 1, 214, 82, 187, 110, 13, 171, 230, 164, 125, 97, 7, 153, 146, 122, 31, 52, 185, 132, 38, 74, 181, 76, 28, 107, 153, 79, 63, 122, 190, 50, 75, 129, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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