Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18bdf5383a3fe9f0342d849f24434ef3ce1c3aae135079f41093496452226737

Tx prefix hash: 657beed17a67536a571944b199cd934c6d4483f52c4e98487a5b9a5413a0d672
Tx public key: 7000832ef2c8d0c2a2e3c91a497f051b1f75d7ff67b197219a94ea33f5bb9ca9
Timestamp: 1587535968 Timestamp [UCT]: 2020-04-22 06:12:48 Age [y:d:h:m:s]: 05:040:13:49:25
Block: 94890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200243 RingCT/type: yes/0
Extra: 017000832ef2c8d0c2a2e3c91a497f051b1f75d7ff67b197219a94ea33f5bb9ca902110000001b4943cd9f000000000000000000

1 output(s) for total of 297.571139237000 dcy

stealth address amount amount idx
00: 638a996b938385e379bb2acac6b0092de23c0195c6151ddd515095a651e79292 297.571139237000 168762 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": 94900, "vin": [ { "gen": { "height": 94890 } } ], "vout": [ { "amount": 297571139237, "target": { "key": "638a996b938385e379bb2acac6b0092de23c0195c6151ddd515095a651e79292" } } ], "extra": [ 1, 112, 0, 131, 46, 242, 200, 208, 194, 162, 227, 201, 26, 73, 127, 5, 27, 31, 117, 215, 255, 103, 177, 151, 33, 154, 148, 234, 51, 245, 187, 156, 169, 2, 17, 0, 0, 0, 27, 73, 67, 205, 159, 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