Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7396e0cb8dd1eb7f1584dd5603879720ba9b56c89bed58ae05d7332a75067280

Tx prefix hash: 8af889c54fd2cc8ac9290411015564b0ccdfc997da3c1735e8612219babf9ee6
Tx public key: 66d32483f1a12cb4b73b9e3bd795aa69bf1d812e703cfc96bad80edd4e6aa33c
Timestamp: 1724217490 Timestamp [UCT]: 2024-08-21 05:18:10 Age [y:d:h:m:s]: 00:274:19:26:33
Block: 1092528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196315 RingCT/type: yes/0
Extra: 0166d32483f1a12cb4b73b9e3bd795aa69bf1d812e703cfc96bad80edd4e6aa33c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf083e9e7cb6b9277ff9da757d0ad7a6ccce09ba19f1e72e3e88f2120f1c4baf 0.600000000000 1567293 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": 1092538, "vin": [ { "gen": { "height": 1092528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf083e9e7cb6b9277ff9da757d0ad7a6ccce09ba19f1e72e3e88f2120f1c4baf" } } ], "extra": [ 1, 102, 211, 36, 131, 241, 161, 44, 180, 183, 59, 158, 59, 215, 149, 170, 105, 191, 29, 129, 46, 112, 60, 252, 150, 186, 216, 14, 221, 78, 106, 163, 60, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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