Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a2e3228abb9e4f243669664b6fe65e5afe6057f5e31876edc4c77e54566731

Tx prefix hash: 79992b29890389933f4881f46b9737f147eb37c6943f8e8eda862a8e29ad14cc
Tx public key: 18943e35bfd7b33dbd4f74b3f8476a4811c1afa1bf1f86781e9dae04956c5a11
Timestamp: 1719512423 Timestamp [UCT]: 2024-06-27 18:20:23 Age [y:d:h:m:s]: 00:353:11:21:42
Block: 1053509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252524 RingCT/type: yes/0
Extra: 0118943e35bfd7b33dbd4f74b3f8476a4811c1afa1bf1f86781e9dae04956c5a1102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75c2e45c8a0edf82a0741e9b4b74cdcae87c6faa74b1a04558ca16fc670af184 0.600000000000 1523856 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": 1053519, "vin": [ { "gen": { "height": 1053509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75c2e45c8a0edf82a0741e9b4b74cdcae87c6faa74b1a04558ca16fc670af184" } } ], "extra": [ 1, 24, 148, 62, 53, 191, 215, 179, 61, 189, 79, 116, 179, 248, 71, 106, 72, 17, 193, 175, 161, 191, 31, 134, 120, 30, 157, 174, 4, 149, 108, 90, 17, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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