Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f66b9b4fe9d6bac55e706a88dbcd22fea2a351b24ac9f4a1278f2f48dab5680

Tx prefix hash: ba1b7d19cb682a2089d1ee356bbd858f7a52acfe9a562d58fbb3c3f90913df38
Tx public key: 0b416c2b759df4c936b42f16d05ec133d97c736afd0506963b0700029ba77f7b
Timestamp: 1719865572 Timestamp [UCT]: 2024-07-01 20:26:12 Age [y:d:h:m:s]: 00:296:08:42:02
Block: 1056436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211779 RingCT/type: yes/0
Extra: 010b416c2b759df4c936b42f16d05ec133d97c736afd0506963b0700029ba77f7b021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 221eef12de779e913fd69d8283689788a08fbf4234d2c9754773a75b9fd65018 0.600000000000 1526849 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": 1056446, "vin": [ { "gen": { "height": 1056436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "221eef12de779e913fd69d8283689788a08fbf4234d2c9754773a75b9fd65018" } } ], "extra": [ 1, 11, 65, 108, 43, 117, 157, 244, 201, 54, 180, 47, 22, 208, 94, 193, 51, 217, 124, 115, 106, 253, 5, 6, 150, 59, 7, 0, 2, 155, 167, 127, 123, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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