Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f66d812bd61b942a1f8180cecf1fa05fc940858aa870cc8261b3321d527d3a66

Tx prefix hash: b3565e46136ab06d2fd9b3eac9f80a4837e3ab0c3bc0c64994edf85b714acb09
Tx public key: fff9f42a697439b371bdf1e2718d1c4c49a630d55bac82533db80f0233fb5972
Timestamp: 1708875084 Timestamp [UCT]: 2024-02-25 15:31:24 Age [y:d:h:m:s]: 01:079:18:13:42
Block: 965334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318037 RingCT/type: yes/0
Extra: 01fff9f42a697439b371bdf1e2718d1c4c49a630d55bac82533db80f0233fb59720211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bd95e469327da49e6cf8fdc1779947ed8c86a3f00a63e1906562439aaceb4aa 0.600000000000 1425083 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": 965344, "vin": [ { "gen": { "height": 965334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bd95e469327da49e6cf8fdc1779947ed8c86a3f00a63e1906562439aaceb4aa" } } ], "extra": [ 1, 255, 249, 244, 42, 105, 116, 57, 179, 113, 189, 241, 226, 113, 141, 28, 76, 73, 166, 48, 213, 91, 172, 130, 83, 61, 184, 15, 2, 51, 251, 89, 114, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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