Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e69ba4bfa3f74431f4a42cbb9b6c021aaf4497e6bd40912f81154972c440b2f3

Tx prefix hash: ab1a01cca280a6bdbe83afebbda55a30be561d86a4b08bac46a0489c39918e4e
Tx public key: fb773b54d3ea0232479e09653c098921d2eef2fc38d2e5d8aa583af014e4295f
Timestamp: 1716943732 Timestamp [UCT]: 2024-05-29 00:48:52 Age [y:d:h:m:s]: 00:294:09:49:41
Block: 1032221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210427 RingCT/type: yes/0
Extra: 01fb773b54d3ea0232479e09653c098921d2eef2fc38d2e5d8aa583af014e4295f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54bd352fcd5defcd66d5309c16da519dc8ffcdc5353baa977737675fac47f2d5 0.600000000000 1500670 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": 1032231, "vin": [ { "gen": { "height": 1032221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54bd352fcd5defcd66d5309c16da519dc8ffcdc5353baa977737675fac47f2d5" } } ], "extra": [ 1, 251, 119, 59, 84, 211, 234, 2, 50, 71, 158, 9, 101, 60, 9, 137, 33, 210, 238, 242, 252, 56, 210, 229, 216, 170, 88, 58, 240, 20, 228, 41, 95, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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