Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2000a2c0a72bb050c7cb93cfaf379f2a877e2f41c78c825d5637e198bfb38d52

Tx prefix hash: 38a7f91ab434e4f0e97141a35a2ee747f9a31966d06b3386712d60994c24a78f
Tx public key: 8aacc2a1165bac103f6e086b275c83bff6c0072c1cc3f568f9171c9e7d1951a5
Timestamp: 1684965353 Timestamp [UCT]: 2023-05-24 21:55:53 Age [y:d:h:m:s]: 01:184:12:58:46
Block: 767361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393276 RingCT/type: yes/0
Extra: 018aacc2a1165bac103f6e086b275c83bff6c0072c1cc3f568f9171c9e7d1951a5021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.759602774000 dcy

stealth address amount amount idx
00: 6d9ea64a4696f93a54aa55afe9ef309a077e62da32fa1ab57a0a2bccd7336302 1.759602774000 1216482 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": 767371, "vin": [ { "gen": { "height": 767361 } } ], "vout": [ { "amount": 1759602774, "target": { "key": "6d9ea64a4696f93a54aa55afe9ef309a077e62da32fa1ab57a0a2bccd7336302" } } ], "extra": [ 1, 138, 172, 194, 161, 22, 91, 172, 16, 63, 110, 8, 107, 39, 92, 131, 191, 246, 192, 7, 44, 28, 195, 245, 104, 249, 23, 28, 158, 125, 25, 81, 165, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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