Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118033ac48df34a4f10b65ca4ad2abe6fc99a19c0214e279a4f4fea6aaf3a7e7

Tx prefix hash: 6daf7e7af00aa794814cad2b9aff9b2aa3172f4d76cb68fe22b067ffd7b1b523
Tx public key: 3e983504c4d05f730bb79ee957ce964faa21a174e4002c641df4ec5d0d899798
Timestamp: 1715401666 Timestamp [UCT]: 2024-05-11 04:27:46 Age [y:d:h:m:s]: 00:309:22:31:15
Block: 1019460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221515 RingCT/type: yes/0
Extra: 013e983504c4d05f730bb79ee957ce964faa21a174e4002c641df4ec5d0d899798021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c5c87088544878ec91e9594c83743ea51145eb8c8f1e8818b8fe91a3664f29c 0.600000000000 1483433 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": 1019470, "vin": [ { "gen": { "height": 1019460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c5c87088544878ec91e9594c83743ea51145eb8c8f1e8818b8fe91a3664f29c" } } ], "extra": [ 1, 62, 152, 53, 4, 196, 208, 95, 115, 11, 183, 158, 233, 87, 206, 150, 79, 170, 33, 161, 116, 228, 0, 44, 100, 29, 244, 236, 93, 13, 137, 151, 152, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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