Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097c7724092e43f484243842e1a9a64cd0e381f11da723c8a8bc33368ad1f0d1

Tx prefix hash: 5897384116fe209cb94cdb4157917ae7ef5c4f4ca96eca18a993ad384aba5fd1
Tx public key: 2a6a64e61269486e1f28688265ee2870ba6eee1583ea1415235733d9d0f1e240
Timestamp: 1694907024 Timestamp [UCT]: 2023-09-16 23:30:24 Age [y:d:h:m:s]: 01:128:22:28:04
Block: 849710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353418 RingCT/type: yes/0
Extra: 012a6a64e61269486e1f28688265ee2870ba6eee1583ea1415235733d9d0f1e24002110000000233af99f4000000000000000000

1 output(s) for total of 0.938767607000 dcy

stealth address amount amount idx
00: a770b9ceb9b846e589f4e2d1b0cba37a91c70cfee98b3e746a03498de177ab5e 0.938767607000 1303388 of 0

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": 849720, "vin": [ { "gen": { "height": 849710 } } ], "vout": [ { "amount": 938767607, "target": { "key": "a770b9ceb9b846e589f4e2d1b0cba37a91c70cfee98b3e746a03498de177ab5e" } } ], "extra": [ 1, 42, 106, 100, 230, 18, 105, 72, 110, 31, 40, 104, 130, 101, 238, 40, 112, 186, 110, 238, 21, 131, 234, 20, 21, 35, 87, 51, 217, 208, 241, 226, 64, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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