Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5cc3ad13915a25bc4b41de9f5e39e327656e89fb3d145f48953ecc2227a258d

Tx prefix hash: ea90929e2f578ed6f2c47aad0ed7914f11651c6b26b21ec255e43f629ec52a76
Tx public key: 669dd6e2ba6f02dac585893d930f2f63c388e5c9eb80286e8982b550120438a6
Timestamp: 1702069901 Timestamp [UCT]: 2023-12-08 21:11:41 Age [y:d:h:m:s]: 01:157:17:16:18
Block: 908905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373904 RingCT/type: yes/0
Extra: 01669dd6e2ba6f02dac585893d930f2f63c388e5c9eb80286e8982b550120438a602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 171a9bc9e46e667482dbd8becb15c97cede4dc6926707914c0957b0c2a5fa7a3 0.600000000000 1365966 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": 908915, "vin": [ { "gen": { "height": 908905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171a9bc9e46e667482dbd8becb15c97cede4dc6926707914c0957b0c2a5fa7a3" } } ], "extra": [ 1, 102, 157, 214, 226, 186, 111, 2, 218, 197, 133, 137, 61, 147, 15, 47, 99, 195, 136, 229, 201, 235, 128, 40, 110, 137, 130, 181, 80, 18, 4, 56, 166, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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