Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c955ba72841343bbbcba144f11c0af45f5c3e6500bf978334e9b97ae5b222df

Tx prefix hash: 4e3dccb90e2e2269770c646091e1e83927870296f9b986c8daf99baa3ca11dac
Tx public key: adf376f773bb0d31a9d34dada8f473caac97ed6fbfe1c9d7cd2f39458858f76e
Timestamp: 1693306536 Timestamp [UCT]: 2023-08-29 10:55:36 Age [y:d:h:m:s]: 01:290:20:51:10
Block: 836428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468966 RingCT/type: yes/0
Extra: 01adf376f773bb0d31a9d34dada8f473caac97ed6fbfe1c9d7cd2f39458858f76e02110000000533af99f4000000000000000000

1 output(s) for total of 1.038883610000 dcy

stealth address amount amount idx
00: a2812bd2053e4e608e4902df862a78446f0ff4778b053a4047bfd3151b1a1531 1.038883610000 1289012 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": 836438, "vin": [ { "gen": { "height": 836428 } } ], "vout": [ { "amount": 1038883610, "target": { "key": "a2812bd2053e4e608e4902df862a78446f0ff4778b053a4047bfd3151b1a1531" } } ], "extra": [ 1, 173, 243, 118, 247, 115, 187, 13, 49, 169, 211, 77, 173, 168, 244, 115, 202, 172, 151, 237, 111, 191, 225, 201, 215, 205, 47, 57, 69, 136, 88, 247, 110, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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