Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7005f18ecda5cb2908ba640c3f1bb2a9c3104d7cbff74b9b018673b8f54def7

Tx prefix hash: 1083903319d7967375e13b68c1528d37360191bf0d7e9c2e9721ae9ca758edd6
Tx public key: 3ac43b8d9a98d2003315759ed85841c99d760abd03ab2f5b1d65d29f5cb541a2
Timestamp: 1657201669 Timestamp [UCT]: 2022-07-07 13:47:49 Age [y:d:h:m:s]: 03:116:17:47:40
Block: 538639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863147 RingCT/type: yes/0
Extra: 013ac43b8d9a98d2003315759ed85841c99d760abd03ab2f5b1d65d29f5cb541a20211000000134da16a3a000000000000000000

1 output(s) for total of 10.075475290000 dcy

stealth address amount amount idx
00: e5dd3ab89a2a99e423948872db58671fea3f88535090cc233d5cf19e66793614 10.075475290000 968664 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": 538649, "vin": [ { "gen": { "height": 538639 } } ], "vout": [ { "amount": 10075475290, "target": { "key": "e5dd3ab89a2a99e423948872db58671fea3f88535090cc233d5cf19e66793614" } } ], "extra": [ 1, 58, 196, 59, 141, 154, 152, 210, 0, 51, 21, 117, 158, 216, 88, 65, 201, 157, 118, 10, 189, 3, 171, 47, 91, 29, 101, 210, 159, 92, 181, 65, 162, 2, 17, 0, 0, 0, 19, 77, 161, 106, 58, 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