Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4452c81abd9eda92bf3f66b5549555734103a53c87e92d89d94356652e58d89

Tx prefix hash: 0a379faf59ff950c15554550a65dfe34a9a1a0416eb7b279074e9d20655f374f
Tx public key: 93776cb07baf315135b59d6e92925c3acdce258b5f908c2081203e1110aaf5c6
Timestamp: 1704796513 Timestamp [UCT]: 2024-01-09 10:35:13 Age [y:d:h:m:s]: 01:077:02:01:21
Block: 931496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316182 RingCT/type: yes/0
Extra: 0193776cb07baf315135b59d6e92925c3acdce258b5f908c2081203e1110aaf5c602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64503707bd15d176a01ce5543bd5b5d1d6b5c51ea3e419f2ea5cbd27c4b6d988 0.600000000000 1389398 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": 931506, "vin": [ { "gen": { "height": 931496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64503707bd15d176a01ce5543bd5b5d1d6b5c51ea3e419f2ea5cbd27c4b6d988" } } ], "extra": [ 1, 147, 119, 108, 176, 123, 175, 49, 81, 53, 181, 157, 110, 146, 146, 92, 58, 205, 206, 37, 139, 95, 144, 140, 32, 129, 32, 62, 17, 16, 170, 245, 198, 2, 17, 0, 0, 0, 4, 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