Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89919b34da8b65261d479b40b6b6a2eb77309dea75bd4535e77234c9c6783aa

Tx prefix hash: 6466dde18ac364331fc535d5c5dee4b5f59eed8ea50a99723ecc0146e2d1fd86
Tx public key: 11ac09fe89628dc1e593f0077606d363859415ea863e825330e57029e8fc3814
Timestamp: 1715986052 Timestamp [UCT]: 2024-05-17 22:47:32 Age [y:d:h:m:s]: 00:345:01:23:48
Block: 1024277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246654 RingCT/type: yes/0
Extra: 0111ac09fe89628dc1e593f0077606d363859415ea863e825330e57029e8fc38140211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76f9e96928f9a8b7baf4378ad2d9ea0bf1f095ba1ba16fa1ec463e7df898def9 0.600000000000 1489898 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": 1024287, "vin": [ { "gen": { "height": 1024277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76f9e96928f9a8b7baf4378ad2d9ea0bf1f095ba1ba16fa1ec463e7df898def9" } } ], "extra": [ 1, 17, 172, 9, 254, 137, 98, 141, 193, 229, 147, 240, 7, 118, 6, 211, 99, 133, 148, 21, 234, 134, 62, 130, 83, 48, 229, 112, 41, 232, 252, 56, 20, 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