Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e9cc394e1770d8468f627eea4097ad9bc805db37747cfc3d8e26e4797aee997

Tx prefix hash: 9ba79eac90e0f9a8284c90fe805106b0d151d3d43b2de2829030850dec4b12a3
Tx public key: 69e6bb7f61eccb03cd45824ce917a682ad5f24cb1156a4d150b823674a0aa081
Timestamp: 1737287990 Timestamp [UCT]: 2025-01-19 11:59:50 Age [y:d:h:m:s]: 00:150:00:31:22
Block: 1200693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106964 RingCT/type: yes/0
Extra: 0169e6bb7f61eccb03cd45824ce917a682ad5f24cb1156a4d150b823674a0aa081021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5b29137f9a4c54e831c6a15aff7a443af56de9c4f5d73f3ddcd1c5e5693586 0.600000000000 1687338 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": 1200703, "vin": [ { "gen": { "height": 1200693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5b29137f9a4c54e831c6a15aff7a443af56de9c4f5d73f3ddcd1c5e5693586" } } ], "extra": [ 1, 105, 230, 187, 127, 97, 236, 203, 3, 205, 69, 130, 76, 233, 23, 166, 130, 173, 95, 36, 203, 17, 86, 164, 209, 80, 184, 35, 103, 74, 10, 160, 129, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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